Fix CI check for unmanaged packages and none coverage#55
Merged
Conversation
…es as covered - `bumpy ci check` no longer fails when only unmanaged packages changed - Packages listed with `none` in bump files now count as covered in strict mode CI checks
|
The changes in this PR will be included in the next version bump.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
bumpy ci checkno longer fails when only unmanaged packages changed — exits cleanly with "No managed packages have changed" instead of erroring with "No bump files found"noneentries count as covered in CI strict mode — previously onlyplan.releaseswas checked, so packages marked withnonein bump files would incorrectly show as uncoveredTest plan